Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59340891dadb3cdba57706f2a5ab30334e85b17f73a288b9e383de26e5488ac0

Tx prefix hash: b596e2b4f364eff72ace614a42eaec3e6c46a0f47193dc516486a43d4682b419
Tx public key: 9b1095ae4e4b2ea2a3082cab9b41ee5484276d4c51abc103ed4d4f2f152117ed
Timestamp: 1723085946 Timestamp [UCT]: 2024-08-08 02:59:06 Age [y:d:h:m:s]: 00:232:04:24:03
Block: 1083144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165817 RingCT/type: yes/0
Extra: 019b1095ae4e4b2ea2a3082cab9b41ee5484276d4c51abc103ed4d4f2f152117ed021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae419c8f62e94f2d6821459030b5f6762f76499216ea501947657f661e8ef265 0.600000000000 1556979 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": 1083154, "vin": [ { "gen": { "height": 1083144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae419c8f62e94f2d6821459030b5f6762f76499216ea501947657f661e8ef265" } } ], "extra": [ 1, 155, 16, 149, 174, 78, 75, 46, 162, 163, 8, 44, 171, 155, 65, 238, 84, 132, 39, 109, 76, 81, 171, 193, 3, 237, 77, 79, 47, 21, 33, 23, 237, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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