Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 702bad7f341e547c41f2c8cf71c8319cb16e237001fbb5f401652769fae95f18

Tx prefix hash: d8903fe6eccb3b513feb3faae88a700fe82d76417e40d3a3d2deaae0a330f22c
Tx public key: d021ca2263cc38d712dff2ea946b2eb0c940528018798d2db7ba21423e1a5670
Timestamp: 1715467402 Timestamp [UCT]: 2024-05-11 22:43:22 Age [y:d:h:m:s]: 00:354:03:15:03
Block: 1020005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253108 RingCT/type: yes/0
Extra: 01d021ca2263cc38d712dff2ea946b2eb0c940528018798d2db7ba21423e1a567002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384c3bbb1b36210da046ed9ca23cd5edf941647e549fbfe1ed8364131e4731c8 0.600000000000 1484064 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": 1020015, "vin": [ { "gen": { "height": 1020005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384c3bbb1b36210da046ed9ca23cd5edf941647e549fbfe1ed8364131e4731c8" } } ], "extra": [ 1, 208, 33, 202, 34, 99, 204, 56, 215, 18, 223, 242, 234, 148, 107, 46, 176, 201, 64, 82, 128, 24, 121, 141, 45, 183, 186, 33, 66, 62, 26, 86, 112, 2, 17, 0, 0, 0, 6, 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