Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c4debdbcd659e1fd8d85323909a907124147dc88fdba959887aa656ad07a7d2

Tx prefix hash: 5f62c94eefb4302d283cfa97add555d5a4f989a936a7a2e5637c537cc28383d5
Tx public key: effd8c711c18e4f674b571424535a3ca594e0b1ffb1bc3cafca4703c429cac7b
Timestamp: 1709173386 Timestamp [UCT]: 2024-02-29 02:23:06 Age [y:d:h:m:s]: 01:048:16:59:48
Block: 967799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295817 RingCT/type: yes/0
Extra: 01effd8c711c18e4f674b571424535a3ca594e0b1ffb1bc3cafca4703c429cac7b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43eddae84d010d3467baeca238765b3f4c51faf1939430dc0f91a1745f884c01 0.600000000000 1427584 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": 967809, "vin": [ { "gen": { "height": 967799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43eddae84d010d3467baeca238765b3f4c51faf1939430dc0f91a1745f884c01" } } ], "extra": [ 1, 239, 253, 140, 113, 28, 24, 228, 246, 116, 181, 113, 66, 69, 53, 163, 202, 89, 78, 11, 31, 251, 27, 195, 202, 252, 164, 112, 60, 66, 156, 172, 123, 2, 17, 0, 0, 0, 4, 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