Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d89cd99536868099c7fde7454f4499dd9996c3970c8c44e80a2e9e43260b39b

Tx prefix hash: b5205938469fb2530b34df66a4bd676455fb70a2e4608a99b8555d767f0096dd
Tx public key: fc34a841c3b651e14e6d3207c0b9e49462b096e927fdda07915070b0535d182b
Timestamp: 1712946032 Timestamp [UCT]: 2024-04-12 18:20:32 Age [y:d:h:m:s]: 01:208:06:41:47
Block: 999050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407532 RingCT/type: yes/0
Extra: 01fc34a841c3b651e14e6d3207c0b9e49462b096e927fdda07915070b0535d182b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8871beb9f042876e66e8a10a5143f1d662e14faad4f4a808b6f284d420e70d43 0.600000000000 1459526 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": 999060, "vin": [ { "gen": { "height": 999050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8871beb9f042876e66e8a10a5143f1d662e14faad4f4a808b6f284d420e70d43" } } ], "extra": [ 1, 252, 52, 168, 65, 195, 182, 81, 225, 78, 109, 50, 7, 192, 185, 228, 148, 98, 176, 150, 233, 39, 253, 218, 7, 145, 80, 112, 176, 83, 93, 24, 43, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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