Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7787ae804a7570d0c00132b48be401bb6b07ec97930083f93e35c430a86fac28

Tx prefix hash: 6b63fed88f3c3c5be2af225c2a1e23f932f9d0b6b20948277ee2ec953efb814d
Tx public key: feca2603b9839d5714cee598a7caee6d464aaa7b52efc8cb6a6a712ee7eed912
Timestamp: 1735013476 Timestamp [UCT]: 2024-12-24 04:11:16 Age [y:d:h:m:s]: 00:107:10:47:23
Block: 1181908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76584 RingCT/type: yes/0
Extra: 01feca2603b9839d5714cee598a7caee6d464aaa7b52efc8cb6a6a712ee7eed9120211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b94e8d570a15daac9894e096a50a87014de2afb1feff6aecc649f61095706d3 0.600000000000 1668337 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": 1181918, "vin": [ { "gen": { "height": 1181908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b94e8d570a15daac9894e096a50a87014de2afb1feff6aecc649f61095706d3" } } ], "extra": [ 1, 254, 202, 38, 3, 185, 131, 157, 87, 20, 206, 229, 152, 167, 202, 238, 109, 70, 74, 170, 123, 82, 239, 200, 203, 106, 106, 113, 46, 231, 238, 217, 18, 2, 17, 0, 0, 0, 3, 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