Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d419f152ab6803b5ff0ecd49e24005bffa04d71b6a727d335e3e04bce4f8ad7

Tx prefix hash: 9b8cfc46e63a2d6f5e3b11a8df44ecfd538fac14f9340080ef056174606cb4bb
Tx public key: ae84b097ca465bf92a0679d1f73c8b3c4805abd9049de4a15dea5972a52298e7
Timestamp: 1723619019 Timestamp [UCT]: 2024-08-14 07:03:39 Age [y:d:h:m:s]: 00:257:15:50:03
Block: 1087567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184040 RingCT/type: yes/0
Extra: 01ae84b097ca465bf92a0679d1f73c8b3c4805abd9049de4a15dea5972a52298e7021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3ca70247623a75a15875688b2086beaec8e060d6fdb9760b4bb04d4b284bda 0.600000000000 1562176 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": 1087577, "vin": [ { "gen": { "height": 1087567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3ca70247623a75a15875688b2086beaec8e060d6fdb9760b4bb04d4b284bda" } } ], "extra": [ 1, 174, 132, 176, 151, 202, 70, 91, 249, 42, 6, 121, 209, 247, 60, 139, 60, 72, 5, 171, 217, 4, 157, 228, 161, 93, 234, 89, 114, 165, 34, 152, 231, 2, 17, 0, 0, 0, 9, 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