Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 560f686edea036a343af0ac570f578ba448385767c31855a9608a669528ed6e3

Tx prefix hash: 473a11283af3c6ca3ac50ea6e10507d1f0b7beb5f76ce083cdd4a4554c0fbe4d
Tx public key: efc53bed6210362ba2dd8eaa3b5b573ba8f228af82cfdd26b5d461ad8c46b3fc
Timestamp: 1742384085 Timestamp [UCT]: 2025-03-19 11:34:45 Age [y:d:h:m:s]: 00:295:09:38:15
Block: 1242673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208916 RingCT/type: yes/0
Extra: 01efc53bed6210362ba2dd8eaa3b5b573ba8f228af82cfdd26b5d461ad8c46b3fc021100000005f7071dc6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ddd6fffce581250543ca06a9676c4ca9e28c9da073c2a3fd4e9d13bc07abc3b 0.600000000000 1729648 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": 1242683, "vin": [ { "gen": { "height": 1242673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ddd6fffce581250543ca06a9676c4ca9e28c9da073c2a3fd4e9d13bc07abc3b" } } ], "extra": [ 1, 239, 197, 59, 237, 98, 16, 54, 43, 162, 221, 142, 170, 59, 91, 87, 59, 168, 242, 40, 175, 130, 207, 221, 38, 181, 212, 97, 173, 140, 70, 179, 252, 2, 17, 0, 0, 0, 5, 247, 7, 29, 198, 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