Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c13e8173e50dfa70d5fc7392b882c474530f446f218fc02069702de6e2927143

Tx prefix hash: 528a9a158cac3ca05ca0e9594e14e2d73f91c21228f4ecaef71bf012c9dba600
Tx public key: 0d3ddc1ccdc4be68788c6607c6a8a97d6c48cc72fd96db0bc53424c75f9bb9aa
Timestamp: 1733406023 Timestamp [UCT]: 2024-12-05 13:40:23 Age [y:d:h:m:s]: 00:100:01:06:40
Block: 1168598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71311 RingCT/type: yes/0
Extra: 010d3ddc1ccdc4be68788c6607c6a8a97d6c48cc72fd96db0bc53424c75f9bb9aa021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5706b3373cca83153aecbe5525650b819076278a8bb062f4942fd6fa08fba414 0.600000000000 1654309 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": 1168608, "vin": [ { "gen": { "height": 1168598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5706b3373cca83153aecbe5525650b819076278a8bb062f4942fd6fa08fba414" } } ], "extra": [ 1, 13, 61, 220, 28, 205, 196, 190, 104, 120, 140, 102, 7, 198, 168, 169, 125, 108, 72, 204, 114, 253, 150, 219, 11, 197, 52, 36, 199, 95, 155, 185, 170, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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