Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4460b5cdb1d9989cdb9e9186d557fca2db01d15211aa46e5f2906f0edf29d3ce

Tx prefix hash: d99e93e2c70599a828b80636436bdb2f13f629fd169fa98b79f1d5099f7d7a37
Tx public key: 0a4edcc3c8a0420fe9c212759388ab6b144bb149db49a8a0f49848be1c63d83a
Timestamp: 1720641621 Timestamp [UCT]: 2024-07-10 20:00:21 Age [y:d:h:m:s]: 00:253:03:15:02
Block: 1062877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180863 RingCT/type: yes/0
Extra: 010a4edcc3c8a0420fe9c212759388ab6b144bb149db49a8a0f49848be1c63d83a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc9c09e521505b1676219c47e86fa6f40495631d82d4bda22ffbce45812d7aa0 0.600000000000 1533388 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": 1062887, "vin": [ { "gen": { "height": 1062877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc9c09e521505b1676219c47e86fa6f40495631d82d4bda22ffbce45812d7aa0" } } ], "extra": [ 1, 10, 78, 220, 195, 200, 160, 66, 15, 233, 194, 18, 117, 147, 136, 171, 107, 20, 75, 177, 73, 219, 73, 168, 160, 244, 152, 72, 190, 28, 99, 216, 58, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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