Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a98c0ed4579bba9a882016298e9ecbc683feeb666ff8933c0235410e6f69f8e5

Tx prefix hash: 325042e3bed1285e2c5c3ef60e7357f647a0e4d97ffac2f4b2a1786e6ac4fbc4
Tx public key: e952613c4b311512d9e17711ecb31386dc687877c5d3f277d6ac385c3225f3e1
Timestamp: 1711365369 Timestamp [UCT]: 2024-03-25 11:16:09 Age [y:d:h:m:s]: 01:228:22:57:09
Block: 986000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422298 RingCT/type: yes/0
Extra: 01e952613c4b311512d9e17711ecb31386dc687877c5d3f277d6ac385c3225f3e10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6a3b786988acae7a6f454b86f0f29008532b66352fedda6a8a23a72edc77725 0.600000000000 1446223 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": 986010, "vin": [ { "gen": { "height": 986000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6a3b786988acae7a6f454b86f0f29008532b66352fedda6a8a23a72edc77725" } } ], "extra": [ 1, 233, 82, 97, 60, 75, 49, 21, 18, 217, 225, 119, 17, 236, 179, 19, 134, 220, 104, 120, 119, 197, 211, 242, 119, 214, 172, 56, 92, 50, 37, 243, 225, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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