Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5afa3202d094b769bc4c29ce9b638b25c0ae9e1f48e5d99d4749fb492a2b789

Tx prefix hash: 6bf13f99c8d8a2c72ccf4ba563b5f9da4e4f5726b1d9c477e017cd500e6a154d
Tx public key: accb3654751f256bf6f09d9ce1460114ff5f2d45e93f82ff464ec82c9217118e
Timestamp: 1738310507 Timestamp [UCT]: 2025-01-31 08:01:47 Age [y:d:h:m:s]: 00:041:15:19:26
Block: 1208934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29796 RingCT/type: yes/0
Extra: 01accb3654751f256bf6f09d9ce1460114ff5f2d45e93f82ff464ec82c9217118e02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc0c3438ef750d83e1c153908c45235da0fed33c6d17f97f1d10f836327a22de 0.600000000000 1695671 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": 1208944, "vin": [ { "gen": { "height": 1208934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc0c3438ef750d83e1c153908c45235da0fed33c6d17f97f1d10f836327a22de" } } ], "extra": [ 1, 172, 203, 54, 84, 117, 31, 37, 107, 246, 240, 157, 156, 225, 70, 1, 20, 255, 95, 45, 69, 233, 63, 130, 255, 70, 78, 200, 44, 146, 23, 17, 142, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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