Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71a0640e29b7f960dff582e5d298ad1ef147d541c05209e35cfe5b1a3ef97deb

Tx prefix hash: 564e1eb68832148e3beefe95d9addad56e6eec79102d727e748e17451dfd6d11
Tx public key: e31a00c31863b75e1cec26e2f5fb8b68cda04d692fc992307da22050500de7fe
Timestamp: 1728537448 Timestamp [UCT]: 2024-10-10 05:17:28 Age [y:d:h:m:s]: 00:200:18:47:28
Block: 1128332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143316 RingCT/type: yes/0
Extra: 01e31a00c31863b75e1cec26e2f5fb8b68cda04d692fc992307da22050500de7fe02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c367c0df0ae7f9fc138fe67538c6c864a8bdcb5c5fed3feb8f88ef49def73d8 0.600000000000 1611149 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": 1128342, "vin": [ { "gen": { "height": 1128332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c367c0df0ae7f9fc138fe67538c6c864a8bdcb5c5fed3feb8f88ef49def73d8" } } ], "extra": [ 1, 227, 26, 0, 195, 24, 99, 183, 94, 28, 236, 38, 226, 245, 251, 139, 104, 205, 160, 77, 105, 47, 201, 146, 48, 125, 162, 32, 80, 80, 13, 231, 254, 2, 17, 0, 0, 0, 4, 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