Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1498b9e535053eee19e5fd2feaa707ed2802e7ee40c4d7476f317cf5a45b793f

Tx prefix hash: 4cd95db98080ebf13826ced5e88cdbe3ac3366879a1a6261eaa17040966b12a4
Tx public key: 72e5c528ad9c64ba490bfbb19e1e01de283b35cab80d2c3dc49d9cf817f0d68a
Timestamp: 1718762345 Timestamp [UCT]: 2024-06-19 01:59:05 Age [y:d:h:m:s]: 01:142:14:11:08
Block: 1047293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360467 RingCT/type: yes/0
Extra: 0172e5c528ad9c64ba490bfbb19e1e01de283b35cab80d2c3dc49d9cf817f0d68a0211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd0e251110444da708f31a40cc6bb788efe54083d60595f91f2e8785795aad1b 0.600000000000 1517112 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": 1047303, "vin": [ { "gen": { "height": 1047293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd0e251110444da708f31a40cc6bb788efe54083d60595f91f2e8785795aad1b" } } ], "extra": [ 1, 114, 229, 197, 40, 173, 156, 100, 186, 73, 11, 251, 177, 158, 30, 1, 222, 40, 59, 53, 202, 184, 13, 44, 61, 196, 157, 156, 248, 23, 240, 214, 138, 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