Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a049ac3a8b9e1167f6ef708824073f1dedb6e81621ce9c4aeafc2bf624910423

Tx prefix hash: d2367234b6f09b3d49b28ec2ee4786704b2a0bedf87f94160b65b9b010996873
Tx public key: f3833f81c705f9d1642f352b7868e95fcceca66b86f85ec4725949c8fb177978
Timestamp: 1724266250 Timestamp [UCT]: 2024-08-21 18:50:50 Age [y:d:h:m:s]: 01:090:13:10:39
Block: 1092932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323174 RingCT/type: yes/0
Extra: 01f3833f81c705f9d1642f352b7868e95fcceca66b86f85ec4725949c8fb177978021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5856471d8e002d2ba81bbb4f1ba1b9b19efd4f3c8b3eed0177aa22f0f4d628cf 0.600000000000 1567777 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": 1092942, "vin": [ { "gen": { "height": 1092932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5856471d8e002d2ba81bbb4f1ba1b9b19efd4f3c8b3eed0177aa22f0f4d628cf" } } ], "extra": [ 1, 243, 131, 63, 129, 199, 5, 249, 209, 100, 47, 53, 43, 120, 104, 233, 95, 204, 236, 166, 107, 134, 248, 94, 196, 114, 89, 73, 200, 251, 23, 121, 120, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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