Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333cbbab6a1d5fa95ea092ec71f80104057a65343610e525e21e3862cd2f5cad

Tx prefix hash: 688b6d4886e334e0bf438c1c105a20472ff8b56f9312dff169709f0ffe03682c
Tx public key: d80659da3c64c52da97e0ab8aa891383126b2fba07659b0cadb56ff8fde9f78a
Timestamp: 1713192814 Timestamp [UCT]: 2024-04-15 14:53:34 Age [y:d:h:m:s]: 01:289:15:24:28
Block: 1001109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465610 RingCT/type: yes/0
Extra: 01d80659da3c64c52da97e0ab8aa891383126b2fba07659b0cadb56ff8fde9f78a02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c31e3c570d36221db654a37b16c91a880f2f8a457cdbe36fd8a4639f9fb6ae9 0.600000000000 1461611 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": 1001119, "vin": [ { "gen": { "height": 1001109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c31e3c570d36221db654a37b16c91a880f2f8a457cdbe36fd8a4639f9fb6ae9" } } ], "extra": [ 1, 216, 6, 89, 218, 60, 100, 197, 45, 169, 126, 10, 184, 170, 137, 19, 131, 18, 107, 47, 186, 7, 101, 155, 12, 173, 181, 111, 248, 253, 233, 247, 138, 2, 17, 0, 0, 0, 6, 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