Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd275b512e2923fe71868817adcc3db2f6f60a7cd20583d94151e172a0edf93

Tx prefix hash: 2c70b492ec4216efca60693a68617628fbd17485f55e322c551319d39277d287
Tx public key: e8c8f8d78e61f7415f5555c39e32e43f6d321db51496a05f377989acc56d9acf
Timestamp: 1711227080 Timestamp [UCT]: 2024-03-23 20:51:20 Age [y:d:h:m:s]: 01:011:15:06:24
Block: 984849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269263 RingCT/type: yes/0
Extra: 01e8c8f8d78e61f7415f5555c39e32e43f6d321db51496a05f377989acc56d9acf0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b19a40ae221092ef70fd1bc0b88273b795e982400e4f800f08b8c15f0c6eab2 0.600000000000 1445022 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": 984859, "vin": [ { "gen": { "height": 984849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b19a40ae221092ef70fd1bc0b88273b795e982400e4f800f08b8c15f0c6eab2" } } ], "extra": [ 1, 232, 200, 248, 215, 142, 97, 247, 65, 95, 85, 85, 195, 158, 50, 228, 63, 109, 50, 29, 181, 20, 150, 160, 95, 55, 121, 137, 172, 197, 109, 154, 207, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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