Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e97a9c24133336d3b282e7428ed60f4beed0f604004eaae01072ab955483cb

Tx prefix hash: 2f2bd08dc605a051f90ee0823c5a1aeda50318044fef4366092c58f739bf24af
Tx public key: fef75a0e1d1dee25a9e1103347ff0f510428eca78f4b8c3778e3c0cf59c40aea
Timestamp: 1713142027 Timestamp [UCT]: 2024-04-15 00:47:07 Age [y:d:h:m:s]: 01:002:07:11:27
Block: 1000676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262605 RingCT/type: yes/0
Extra: 01fef75a0e1d1dee25a9e1103347ff0f510428eca78f4b8c3778e3c0cf59c40aea0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f05d5e4e7b1df04455cd74bc4386c2bf3414501839e7fd26e73a13e56871bce 0.600000000000 1461174 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": 1000686, "vin": [ { "gen": { "height": 1000676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f05d5e4e7b1df04455cd74bc4386c2bf3414501839e7fd26e73a13e56871bce" } } ], "extra": [ 1, 254, 247, 90, 14, 29, 29, 238, 37, 169, 225, 16, 51, 71, 255, 15, 81, 4, 40, 236, 167, 143, 75, 140, 55, 120, 227, 192, 207, 89, 196, 10, 234, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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