Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e72a6e705400d7fdd74c9ab08db328e0b181a5a8b561075d8c8019915180755

Tx prefix hash: 502a1843a5758d1e52d4cb66b15d7100f2fd32ab7b53190ca86c975b6b1ee3cd
Tx public key: c70d859e257cd24d5384f2b142cb4fb019ce0d4abeafad79ee1c6af716670701
Timestamp: 1731753193 Timestamp [UCT]: 2024-11-16 10:33:13 Age [y:d:h:m:s]: 00:135:03:27:25
Block: 1154908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96400 RingCT/type: yes/0
Extra: 01c70d859e257cd24d5384f2b142cb4fb019ce0d4abeafad79ee1c6af7166707010211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1675dc0b91f9ae1e444783076e838837abdd1378902c063cde2099022c2e43a3 0.600000000000 1640521 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": 1154918, "vin": [ { "gen": { "height": 1154908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1675dc0b91f9ae1e444783076e838837abdd1378902c063cde2099022c2e43a3" } } ], "extra": [ 1, 199, 13, 133, 158, 37, 124, 210, 77, 83, 132, 242, 177, 66, 203, 79, 176, 25, 206, 13, 74, 190, 175, 173, 121, 238, 28, 106, 247, 22, 103, 7, 1, 2, 17, 0, 0, 0, 7, 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