Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a5f92f7963c0f1fa485ed1f6950eb5deb430930c5c2f8a3915275fe8a70a23

Tx prefix hash: 9254e3086c733ee7141c490108f2cbc30f6108c6b874e958b3f40977a71c6162
Tx public key: 3f1f506bafd24cf34f4cc2ac64f8bbaf9b7d561ef91df431245aea161c233e66
Timestamp: 1724539194 Timestamp [UCT]: 2024-08-24 22:39:54 Age [y:d:h:m:s]: 00:225:18:56:12
Block: 1095211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161200 RingCT/type: yes/0
Extra: 013f1f506bafd24cf34f4cc2ac64f8bbaf9b7d561ef91df431245aea161c233e66021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea742a9fc2a79aadf52589e89d9d4c81f6cb93c678e47809dbaad8b9a607a433 0.600000000000 1570364 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": 1095221, "vin": [ { "gen": { "height": 1095211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea742a9fc2a79aadf52589e89d9d4c81f6cb93c678e47809dbaad8b9a607a433" } } ], "extra": [ 1, 63, 31, 80, 107, 175, 210, 76, 243, 79, 76, 194, 172, 100, 248, 187, 175, 155, 125, 86, 30, 249, 29, 244, 49, 36, 90, 234, 22, 28, 35, 62, 102, 2, 17, 0, 0, 0, 3, 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