Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cc706168c870d246521d120325d062dc9011e90eeb3c181fa48164b1fc01be

Tx prefix hash: 537418d9c82edc8d7996ec0a0ecb924e532b4c4c32d08e205f734ee16b4e8e6c
Tx public key: 3363796ce17ba97e04d7cfb1da52528912af44e2a5d9ab284966caa170377cae
Timestamp: 1741357701 Timestamp [UCT]: 2025-03-07 14:28:21 Age [y:d:h:m:s]: 00:258:13:59:43
Block: 1234165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182535 RingCT/type: yes/0
Extra: 013363796ce17ba97e04d7cfb1da52528912af44e2a5d9ab284966caa170377cae0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808eae038aa8009953b2908edf0a0c16b9d358c5c4f6d75f4818a59e6383a22c 0.600000000000 1721090 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": 1234175, "vin": [ { "gen": { "height": 1234165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808eae038aa8009953b2908edf0a0c16b9d358c5c4f6d75f4818a59e6383a22c" } } ], "extra": [ 1, 51, 99, 121, 108, 225, 123, 169, 126, 4, 215, 207, 177, 218, 82, 82, 137, 18, 175, 68, 226, 165, 217, 171, 40, 73, 102, 202, 161, 112, 55, 124, 174, 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