Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248b9bed7b46dc8951803d990959e2ebbd228237d08482828f3382c2ce10405b

Tx prefix hash: 54bccc68e87698517633a3b18a1f847178fb5bbe64cd2efbc5f0ed0b2da56cfc
Tx public key: 6a693e22e723f979417ebabe142e6a12051ae54a05f04f0baf9a7d541d46097a
Timestamp: 1722961727 Timestamp [UCT]: 2024-08-06 16:28:47 Age [y:d:h:m:s]: 00:312:19:01:54
Block: 1082105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223399 RingCT/type: yes/0
Extra: 016a693e22e723f979417ebabe142e6a12051ae54a05f04f0baf9a7d541d46097a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35960ed946bfb7e460c4583f66d27580881cd0013f9273e954e6313e0a24e03 0.600000000000 1555928 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": 1082115, "vin": [ { "gen": { "height": 1082105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35960ed946bfb7e460c4583f66d27580881cd0013f9273e954e6313e0a24e03" } } ], "extra": [ 1, 106, 105, 62, 34, 231, 35, 249, 121, 65, 126, 186, 190, 20, 46, 106, 18, 5, 26, 229, 74, 5, 240, 79, 11, 175, 154, 125, 84, 29, 70, 9, 122, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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