Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9b9c1362b7f80f8e8f1b58f4d25d722f80fc4226fafc59ca088bb09528e9a80

Tx prefix hash: f53025e9347f16b61d373adbbab40762569389de81ddd7123b6e0f737bec0697
Tx public key: 9f0e92616d01b19d419d195eab70483095a2b4bf08091a97ae2e2d0ed751431f
Timestamp: 1735382001 Timestamp [UCT]: 2024-12-28 10:33:21 Age [y:d:h:m:s]: 00:093:22:23:22
Block: 1184954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66912 RingCT/type: yes/0
Extra: 019f0e92616d01b19d419d195eab70483095a2b4bf08091a97ae2e2d0ed751431f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a8d96f71c4eca47ed09aacce88b3f353c9878f3eb80a880fdbbe2184b145e6 0.600000000000 1671417 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": 1184964, "vin": [ { "gen": { "height": 1184954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a8d96f71c4eca47ed09aacce88b3f353c9878f3eb80a880fdbbe2184b145e6" } } ], "extra": [ 1, 159, 14, 146, 97, 109, 1, 177, 157, 65, 157, 25, 94, 171, 112, 72, 48, 149, 162, 180, 191, 8, 9, 26, 151, 174, 46, 45, 14, 215, 81, 67, 31, 2, 17, 0, 0, 0, 4, 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