Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23cf513e90c7a0a454ed365aa5810afda961c9ef51362c562d3a243a4852485

Tx prefix hash: 728c4fc62b8a2d0e86e1625fcc1223377c347ef6c931932c4437c225db0908a8
Tx public key: 0f951ecb101e282d4ffaae4b5503f66540524a2f31bdb1ca104b48dadcca76c9
Timestamp: 1718699403 Timestamp [UCT]: 2024-06-18 08:30:03 Age [y:d:h:m:s]: 00:293:10:52:37
Block: 1046773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209688 RingCT/type: yes/0
Extra: 010f951ecb101e282d4ffaae4b5503f66540524a2f31bdb1ca104b48dadcca76c90211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eafd529d3aeb7ffa35ce5398c04ac33f2c0677fa974497dfb988c0b45a76c1d2 0.600000000000 1516592 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": 1046783, "vin": [ { "gen": { "height": 1046773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eafd529d3aeb7ffa35ce5398c04ac33f2c0677fa974497dfb988c0b45a76c1d2" } } ], "extra": [ 1, 15, 149, 30, 203, 16, 30, 40, 45, 79, 250, 174, 75, 85, 3, 246, 101, 64, 82, 74, 47, 49, 189, 177, 202, 16, 75, 72, 218, 220, 202, 118, 201, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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