Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8a1c50c908c49934a241ff46f685c75e7591daf96ecdb8ad18276f40cef215

Tx prefix hash: b6237f0c583856b3a2a6bd072252caa76e43a2e5dfd967a6af31df952f353da6
Tx public key: 6b50acfd6eb1ef544e6d229ef4c1c0e928be713d5fbf7ea3d95bf6e2c6af18bb
Timestamp: 1737121563 Timestamp [UCT]: 2025-01-17 13:46:03 Age [y:d:h:m:s]: 00:058:03:30:15
Block: 1199350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41348 RingCT/type: yes/0
Extra: 016b50acfd6eb1ef544e6d229ef4c1c0e928be713d5fbf7ea3d95bf6e2c6af18bb021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31933fe609a11a49e1fb229fe73811463f34f5ba59133c9ee470ce4143a2407c 0.600000000000 1685981 of 15

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": 1199360, "vin": [ { "gen": { "height": 1199350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31933fe609a11a49e1fb229fe73811463f34f5ba59133c9ee470ce4143a2407c" } } ], "extra": [ 1, 107, 80, 172, 253, 110, 177, 239, 84, 78, 109, 34, 158, 244, 193, 192, 233, 40, 190, 113, 61, 95, 191, 126, 163, 217, 91, 246, 226, 198, 175, 24, 187, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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