Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17023aba63033ba21b4f4e58470175ee3f6f14a3e8b69a74bd7bd82435b7667c

Tx prefix hash: bc9417c08db4fc33cbf4194ebd95f24292692f92a2c3f119a94ffff26b72dc43
Tx public key: f0e527ffb3423005a272dd3f481043a516fd230029abcbc9b35d4f37e099325a
Timestamp: 1716015199 Timestamp [UCT]: 2024-05-18 06:53:19 Age [y:d:h:m:s]: 00:336:01:51:43
Block: 1024525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240220 RingCT/type: yes/0
Extra: 01f0e527ffb3423005a272dd3f481043a516fd230029abcbc9b35d4f37e099325a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 014bb9ddcb2bae24ab9536441dcbc1e27a1dc574e800d0d3ea5ca9e2a29b2de5 0.600000000000 1490332 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": 1024535, "vin": [ { "gen": { "height": 1024525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "014bb9ddcb2bae24ab9536441dcbc1e27a1dc574e800d0d3ea5ca9e2a29b2de5" } } ], "extra": [ 1, 240, 229, 39, 255, 179, 66, 48, 5, 162, 114, 221, 63, 72, 16, 67, 165, 22, 253, 35, 0, 41, 171, 203, 201, 179, 93, 79, 55, 224, 153, 50, 90, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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