Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b07183cd5402a1f445e691332de8a8c386ad77e7ef20c4adbf309393cbb9f9

Tx prefix hash: fe43f0ae3435d4c9428887d760b45708d3f893b12bdc5250941e7b9f39f40e24
Tx public key: a7bcf2f234bd4daec06bf95a43428d28f90bfc8001afb8a282525d0096c5d10e
Timestamp: 1736563368 Timestamp [UCT]: 2025-01-11 02:42:48 Age [y:d:h:m:s]: 00:079:19:17:58
Block: 1194729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56821 RingCT/type: yes/0
Extra: 01a7bcf2f234bd4daec06bf95a43428d28f90bfc8001afb8a282525d0096c5d10e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fdbaa2a0c231f438d831273e27d8da3bbb99fc1acaad51f1e98981bfb2effdd 0.600000000000 1681306 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": 1194739, "vin": [ { "gen": { "height": 1194729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fdbaa2a0c231f438d831273e27d8da3bbb99fc1acaad51f1e98981bfb2effdd" } } ], "extra": [ 1, 167, 188, 242, 242, 52, 189, 77, 174, 192, 107, 249, 90, 67, 66, 141, 40, 249, 11, 252, 128, 1, 175, 184, 162, 130, 82, 93, 0, 150, 197, 209, 14, 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