Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0420b31411b9638bf542e2e3497b5a073fa866fb8ae872ed3d7a1c53dca814c

Tx prefix hash: 66adcdb8d8b5981175d03e34deb5e2873a53e596c2a3349f69694358b1857316
Tx public key: 03380014e18aa8a6601e7931dc0a4c3760fc4065d82703507184e604494ed9cf
Timestamp: 1708141329 Timestamp [UCT]: 2024-02-17 03:42:09 Age [y:d:h:m:s]: 00:332:23:08:01
Block: 959231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238369 RingCT/type: yes/0
Extra: 0103380014e18aa8a6601e7931dc0a4c3760fc4065d82703507184e604494ed9cf0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6635529f5eaf279dc7ab8c7ca15c4a78ae768a197cb948c6ab8a03bd3de41f29 0.600000000000 1418762 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": 959241, "vin": [ { "gen": { "height": 959231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6635529f5eaf279dc7ab8c7ca15c4a78ae768a197cb948c6ab8a03bd3de41f29" } } ], "extra": [ 1, 3, 56, 0, 20, 225, 138, 168, 166, 96, 30, 121, 49, 220, 10, 76, 55, 96, 252, 64, 101, 216, 39, 3, 80, 113, 132, 230, 4, 73, 78, 217, 207, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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