Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8452491660f5741d274575eead4e241ee7e398d34aa0b95788e648587e2b33

Tx prefix hash: d4f1d292943da2bd3ff26df98dabaf5c2c4c19358322d24cbebef9029d581b39
Tx public key: 6cf00ebb21e8cb86f7ecf51d0139e1ee5a4c1417d7a921b382cce10a1c8dcf53
Timestamp: 1577896428 Timestamp [UCT]: 2020-01-01 16:33:48 Age [y:d:h:m:s]: 05:166:19:46:23
Block: 36441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1269083 RingCT/type: yes/0
Extra: 016cf00ebb21e8cb86f7ecf51d0139e1ee5a4c1417d7a921b382cce10a1c8dcf5302110000000a4ac5aa02000000000000000000

1 output(s) for total of 464.789911035000 dcy

stealth address amount amount idx
00: 1ecd15c19dff3c567a78b7c06b9c0650c8e38b0e9cca9af83cd364e309c2ce03 464.789911035000 61736 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": 36451, "vin": [ { "gen": { "height": 36441 } } ], "vout": [ { "amount": 464789911035, "target": { "key": "1ecd15c19dff3c567a78b7c06b9c0650c8e38b0e9cca9af83cd364e309c2ce03" } } ], "extra": [ 1, 108, 240, 14, 187, 33, 232, 203, 134, 247, 236, 245, 29, 1, 57, 225, 238, 90, 76, 20, 23, 215, 169, 33, 179, 130, 204, 225, 10, 28, 141, 207, 83, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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