Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc397e361cc3de988313626d51baf6c6c363f9fd514fb660863c57fb33a3405c

Tx prefix hash: 7fb8276577e3c031d22e6c670058a48ebb13430a2256b9e81ca5ea19478e32f8
Tx public key: 36b22af3f6ada9b56032397666f9ca51daf4b5bde39524b2e3a3fbfc72208b44
Timestamp: 1675594409 Timestamp [UCT]: 2023-02-05 10:53:29 Age [y:d:h:m:s]: 02:097:02:53:04
Block: 690290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591056 RingCT/type: yes/0
Extra: 0136b22af3f6ada9b56032397666f9ca51daf4b5bde39524b2e3a3fbfc72208b440211000000045029cbac000000000000000000

1 output(s) for total of 3.167981264000 dcy

stealth address amount amount idx
00: aeac40fb0c39e3c9ef1ebb326d5830e2e53e9b81091411221e6c41ce6a12601b 3.167981264000 1133012 of 0

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": 690300, "vin": [ { "gen": { "height": 690290 } } ], "vout": [ { "amount": 3167981264, "target": { "key": "aeac40fb0c39e3c9ef1ebb326d5830e2e53e9b81091411221e6c41ce6a12601b" } } ], "extra": [ 1, 54, 178, 42, 243, 246, 173, 169, 181, 96, 50, 57, 118, 102, 249, 202, 81, 218, 244, 181, 189, 227, 149, 36, 178, 227, 163, 251, 252, 114, 32, 139, 68, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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