Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb558519a0480f909a291deca5b2faf0eca1db869d4bd9d581cb164dab9229e5

Tx prefix hash: a57802403dfb374429a97ff791398e861f9ca4e8580b64fa3406b4f8ffa17dee
Tx public key: 781b46614c53e8a793641bf51791de3238653eacc0ee9d5aa2332d7b916d5191
Timestamp: 1719633867 Timestamp [UCT]: 2024-06-29 04:04:27 Age [y:d:h:m:s]: 00:275:14:27:15
Block: 1054517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196926 RingCT/type: yes/0
Extra: 01781b46614c53e8a793641bf51791de3238653eacc0ee9d5aa2332d7b916d519102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12e0435d082b96f9aa2cd1705630514b1fbfc43e64fcddb3aa86d788a32dd3d3 0.600000000000 1524880 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": 1054527, "vin": [ { "gen": { "height": 1054517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12e0435d082b96f9aa2cd1705630514b1fbfc43e64fcddb3aa86d788a32dd3d3" } } ], "extra": [ 1, 120, 27, 70, 97, 76, 83, 232, 167, 147, 100, 27, 245, 23, 145, 222, 50, 56, 101, 62, 172, 192, 238, 157, 90, 162, 51, 45, 123, 145, 109, 81, 145, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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