Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a6579459100b7a44ca409739526209115cfa33bf4291ac2c9a5b6427de36eeb

Tx prefix hash: 820a0fb29114ff9fd2df8111d55871851a574a654b1a56a6b87494c3d79eac06
Tx public key: 7ed8e8d98b10f97ee52f457e9ae5b67cc5c0e66e48f6aa0caba6264cd8f875c9
Timestamp: 1735839503 Timestamp [UCT]: 2025-01-02 17:38:23 Age [y:d:h:m:s]: 00:167:06:57:05
Block: 1188740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119268 RingCT/type: yes/0
Extra: 017ed8e8d98b10f97ee52f457e9ae5b67cc5c0e66e48f6aa0caba6264cd8f875c90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 525150e41f8cff2d0ff61a36bc81b96fd92891a9c57a7908db11cc6c4d9fd422 0.600000000000 1675243 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": 1188750, "vin": [ { "gen": { "height": 1188740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "525150e41f8cff2d0ff61a36bc81b96fd92891a9c57a7908db11cc6c4d9fd422" } } ], "extra": [ 1, 126, 216, 232, 217, 139, 16, 249, 126, 229, 47, 69, 126, 154, 229, 182, 124, 197, 192, 230, 110, 72, 246, 170, 12, 171, 166, 38, 76, 216, 248, 117, 201, 2, 17, 0, 0, 0, 3, 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