Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67582ca10ebfbdfb8956d44010055f6b36df4cc8ed9f8030da961f6d8a1dc971

Tx prefix hash: b63e3fe4f597973d0c5e7673ea264aec443dc70e2595da2622cb8d5746c9122f
Tx public key: f72abc5ebdb4e6c79b21e3668ca4bffebf3f30c6d841f1e30a80d1a8cfc691e0
Timestamp: 1718972839 Timestamp [UCT]: 2024-06-21 12:27:19 Age [y:d:h:m:s]: 01:141:18:44:38
Block: 1049016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359909 RingCT/type: yes/0
Extra: 01f72abc5ebdb4e6c79b21e3668ca4bffebf3f30c6d841f1e30a80d1a8cfc691e002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba8875e427bed9adf0e0b7384b8ce3e5ddda717c9b9f35cfb594d72d3b20e744 0.600000000000 1519113 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": 1049026, "vin": [ { "gen": { "height": 1049016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba8875e427bed9adf0e0b7384b8ce3e5ddda717c9b9f35cfb594d72d3b20e744" } } ], "extra": [ 1, 247, 42, 188, 94, 189, 180, 230, 199, 155, 33, 227, 102, 140, 164, 191, 254, 191, 63, 48, 198, 216, 65, 241, 227, 10, 128, 209, 168, 207, 198, 145, 224, 2, 17, 0, 0, 0, 3, 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