Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77717e93b639ba48e0e7562b2893b1c19379f1964f847d69c7dcb608c41718e

Tx prefix hash: fb99d427a7c5afe1c0704db0dd2a4eb50f47d831304a5acd42291fb1cd0a2f2b
Tx public key: 192642212234727bddb2da6c2d20a20d5140bbdeb191c73d90a00ec1e44d0d0b
Timestamp: 1737566722 Timestamp [UCT]: 2025-01-22 17:25:22 Age [y:d:h:m:s]: 00:146:08:58:13
Block: 1202993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104362 RingCT/type: yes/0
Extra: 01192642212234727bddb2da6c2d20a20d5140bbdeb191c73d90a00ec1e44d0d0b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 558fd4a6d050e78a297af6e130a9c0fb723eb1dc66dd5ffc5f6ed56d73940bab 0.600000000000 1689664 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": 1203003, "vin": [ { "gen": { "height": 1202993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558fd4a6d050e78a297af6e130a9c0fb723eb1dc66dd5ffc5f6ed56d73940bab" } } ], "extra": [ 1, 25, 38, 66, 33, 34, 52, 114, 123, 221, 178, 218, 108, 45, 32, 162, 13, 81, 64, 187, 222, 177, 145, 199, 61, 144, 160, 14, 193, 228, 77, 13, 11, 2, 17, 0, 0, 0, 2, 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