Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aa263368a1c782e56f535d7734f3328f242137a2761eb172fb869bd631562f2

Tx prefix hash: 842b4fc3c204483f783df7b07cf8d1f9020f4d4862377911eb576ab02d8b1860
Tx public key: 7755202e5e6f331f9c548aac8b47eb4eb576306fc82cbdcc9cb73fab357a7e5a
Timestamp: 1716523886 Timestamp [UCT]: 2024-05-24 04:11:26 Age [y:d:h:m:s]: 00:299:06:52:27
Block: 1028750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213912 RingCT/type: yes/0
Extra: 017755202e5e6f331f9c548aac8b47eb4eb576306fc82cbdcc9cb73fab357a7e5a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 388c0518b1bd364e8ce275bfb5d69dc1010d9bb89ad0476f06b39c4f0a884578 0.600000000000 1496747 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": 1028760, "vin": [ { "gen": { "height": 1028750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "388c0518b1bd364e8ce275bfb5d69dc1010d9bb89ad0476f06b39c4f0a884578" } } ], "extra": [ 1, 119, 85, 32, 46, 94, 111, 51, 31, 156, 84, 138, 172, 139, 71, 235, 78, 181, 118, 48, 111, 200, 44, 189, 204, 156, 183, 63, 171, 53, 122, 126, 90, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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