Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd312d52946e0ab963cf37bedd07f76b1bc48eed53ce7a2e5911df1c8d21d4ed

Tx prefix hash: 389a604e33200dbb3a05212fae193b4d9ef1160fb650b192409f5e24816c80e6
Tx public key: cee17f6b7236e9f019a57b37a64e135be0a62680c5a6566a201e693a939e6a2e
Timestamp: 1705853616 Timestamp [UCT]: 2024-01-21 16:13:36 Age [y:d:h:m:s]: 01:316:01:47:21
Block: 940248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484754 RingCT/type: yes/0
Extra: 01cee17f6b7236e9f019a57b37a64e135be0a62680c5a6566a201e693a939e6a2e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b222b4ef4a07f6b182d1737a7bc03cef4bbfcdd23a49dc6c5691a714fc21f91 0.600000000000 1398382 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": 940258, "vin": [ { "gen": { "height": 940248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b222b4ef4a07f6b182d1737a7bc03cef4bbfcdd23a49dc6c5691a714fc21f91" } } ], "extra": [ 1, 206, 225, 127, 107, 114, 54, 233, 240, 25, 165, 123, 55, 166, 78, 19, 91, 224, 166, 38, 128, 197, 166, 86, 106, 32, 30, 105, 58, 147, 158, 106, 46, 2, 17, 0, 0, 0, 4, 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