Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fe51c2f976b4bd8ac902d6d043a5b9070177d5486573a4a41f6b70417eba2e8

Tx prefix hash: c91854a704497c4dc3c117698891c249e24c9d4f40ab6dacb0910b847bfa8529
Tx public key: eac5151a31a4221616b60efc2b5bea30e59349a6ec22708fb112563e0543427c
Timestamp: 1730272820 Timestamp [UCT]: 2024-10-30 07:20:20 Age [y:d:h:m:s]: 00:029:03:17:10
Block: 1142652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20844 RingCT/type: yes/0
Extra: 01eac5151a31a4221616b60efc2b5bea30e59349a6ec22708fb112563e0543427c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25765e6246fbd10b153a56a3314ae9d9ce483376192d8f99fc0486e962e6227b 0.600000000000 1626507 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": 1142662, "vin": [ { "gen": { "height": 1142652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25765e6246fbd10b153a56a3314ae9d9ce483376192d8f99fc0486e962e6227b" } } ], "extra": [ 1, 234, 197, 21, 26, 49, 164, 34, 22, 22, 182, 14, 252, 43, 91, 234, 48, 229, 147, 73, 166, 236, 34, 112, 143, 177, 18, 86, 62, 5, 67, 66, 124, 2, 17, 0, 0, 0, 1, 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