Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9530a5ed1b3a09a23ebb952c38f33c1d236b0416793673afa8f60219fda02db3

Tx prefix hash: 2edea99ca0917c2bc53450024d29ee4e548ac4dfba5d8dbe3a4e2aa1dc181bb2
Tx public key: b7a9fd58e7385c7b34fa2d57ef84efb787cdefca64caaa2947252504232e1e66
Timestamp: 1578185391 Timestamp [UCT]: 2020-01-05 00:49:51 Age [y:d:h:m:s]: 05:036:08:21:13
Block: 38884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175805 RingCT/type: yes/0
Extra: 01b7a9fd58e7385c7b34fa2d57ef84efb787cdefca64caaa2947252504232e1e6602110000000e17786bcf000000000000000000

1 output(s) for total of 456.207074566000 dcy

stealth address amount amount idx
00: 0f6419900753818454b76cdca2969f067863b61c330218ce4d4430a5f120aee2 456.207074566000 66639 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 38894, "vin": [ { "gen": { "height": 38884 } } ], "vout": [ { "amount": 456207074566, "target": { "key": "0f6419900753818454b76cdca2969f067863b61c330218ce4d4430a5f120aee2" } } ], "extra": [ 1, 183, 169, 253, 88, 231, 56, 92, 123, 52, 250, 45, 87, 239, 132, 239, 183, 135, 205, 239, 202, 100, 202, 170, 41, 71, 37, 37, 4, 35, 46, 30, 102, 2, 17, 0, 0, 0, 14, 23, 120, 107, 207, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8