Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e98a92ca7b69bb118f4f38758318f7e2f61b08861608f2aecdd6a1883f2e45

Tx prefix hash: e277319b9cc8a65afdb587a53078305a9933691c90c4d3f3c403d370c424c976
Tx public key: 6653e9d578d6db8a340ffcd3545f2fd9520cc3aae920fb223f7b2e526f1162c0
Timestamp: 1576644510 Timestamp [UCT]: 2019-12-18 04:48:30 Age [y:d:h:m:s]: 04:279:08:05:36
Block: 28633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086327 RingCT/type: yes/0
Extra: 016653e9d578d6db8a340ffcd3545f2fd9520cc3aae920fb223f7b2e526f1162c0021100000029ad433a0b000000000000000000

1 output(s) for total of 493.319007596000 dcy

stealth address amount amount idx
00: 7bb9dcfebc14088bb56fa1b0fdbf922d5f9bcd05d396c4637251e4a64db7940a 493.319007596000 47191 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": 28643, "vin": [ { "gen": { "height": 28633 } } ], "vout": [ { "amount": 493319007596, "target": { "key": "7bb9dcfebc14088bb56fa1b0fdbf922d5f9bcd05d396c4637251e4a64db7940a" } } ], "extra": [ 1, 102, 83, 233, 213, 120, 214, 219, 138, 52, 15, 252, 211, 84, 95, 47, 217, 82, 12, 195, 170, 233, 32, 251, 34, 63, 123, 46, 82, 111, 17, 98, 192, 2, 17, 0, 0, 0, 41, 173, 67, 58, 11, 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