Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 602a5bec2013b584b495bcb53b032363f27be35ad8a749522f1718bcfa28a9ad

Tx prefix hash: 3ce5e5c52dc8e70e5d137813ea0111b6b038ff1a494e6dfa7764c8108eff717b
Tx public key: ffcb2aa132724e14aecc905c9e334b08b58f42eaa901027fa777ab804126890a
Timestamp: 1737507169 Timestamp [UCT]: 2025-01-22 00:52:49 Age [y:d:h:m:s]: 00:147:11:34:14
Block: 1202504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105153 RingCT/type: yes/0
Extra: 01ffcb2aa132724e14aecc905c9e334b08b58f42eaa901027fa777ab804126890a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1df328aa11d17f1c3c405bed3bfd540bf3ffcaadc8f40f94db42cd5f68c8a9 0.600000000000 1689169 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": 1202514, "vin": [ { "gen": { "height": 1202504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1df328aa11d17f1c3c405bed3bfd540bf3ffcaadc8f40f94db42cd5f68c8a9" } } ], "extra": [ 1, 255, 203, 42, 161, 50, 114, 78, 20, 174, 204, 144, 92, 158, 51, 75, 8, 181, 143, 66, 234, 169, 1, 2, 127, 167, 119, 171, 128, 65, 38, 137, 10, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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