Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dccae2f034ca4ce2907ea715aebfc002d362830c8e88dc8baec2f9a8159073d9

Tx prefix hash: ba111805cfc747757e435267390c6a639344f3dcd528d2666c715dc342129ab3
Tx public key: 6ca0799b2333ec041ad3a05b6da2056b0a5676d65d33d671868dbf8a998c8de6
Timestamp: 1695044890 Timestamp [UCT]: 2023-09-18 13:48:10 Age [y:d:h:m:s]: 01:268:00:44:32
Block: 850860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452649 RingCT/type: yes/0
Extra: 016ca0799b2333ec041ad3a05b6da2056b0a5676d65d33d671868dbf8a998c8de60211000000084b8f5122000000000000000000

1 output(s) for total of 0.930567041000 dcy

stealth address amount amount idx
00: 51408bc08c2b4c0a62f82f8e73849b49d8c86a71d63e57f440122dc79db0c02d 0.930567041000 1304604 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": 850870, "vin": [ { "gen": { "height": 850860 } } ], "vout": [ { "amount": 930567041, "target": { "key": "51408bc08c2b4c0a62f82f8e73849b49d8c86a71d63e57f440122dc79db0c02d" } } ], "extra": [ 1, 108, 160, 121, 155, 35, 51, 236, 4, 26, 211, 160, 91, 109, 162, 5, 107, 10, 86, 118, 214, 93, 51, 214, 113, 134, 141, 191, 138, 153, 140, 141, 230, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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