Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfdaea29d551499f82934a9ad1818a264373473c3f3edafe75e8e0a661b942d

Tx prefix hash: 5dcc76fa4c2e49d90a9251f9f43e9f9457f4729ddcda1692e0d519c007e7b7c3
Tx public key: fef170c2f608dc7933cf04aa50e88881b5bee80e08ec6dcc82eee62832991ca8
Timestamp: 1723190303 Timestamp [UCT]: 2024-08-09 07:58:23 Age [y:d:h:m:s]: 00:241:13:58:47
Block: 1084001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172537 RingCT/type: yes/0
Extra: 01fef170c2f608dc7933cf04aa50e88881b5bee80e08ec6dcc82eee62832991ca802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb8688f772438aede8c2dffa215af11b50dc09ac4f88d5232cb12fca8369d08c 0.600000000000 1558122 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": 1084011, "vin": [ { "gen": { "height": 1084001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb8688f772438aede8c2dffa215af11b50dc09ac4f88d5232cb12fca8369d08c" } } ], "extra": [ 1, 254, 241, 112, 194, 246, 8, 220, 121, 51, 207, 4, 170, 80, 232, 136, 129, 181, 190, 232, 14, 8, 236, 109, 204, 130, 238, 230, 40, 50, 153, 28, 168, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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