Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb1bab10ba8dc8c6999fa4a32bf3c4d5984173251415f4291454006e013f97c

Tx prefix hash: e12f9724ac029ea4a9e2fd27ffb58f268021f134908e06c947d1ad5b61e9b978
Tx public key: 035a0368d017200e41def9f63d91d22b499a4c7e01bfebf275bd0701d12dd544
Timestamp: 1750456898 Timestamp [UCT]: 2025-06-20 22:01:38 Age [y:d:h:m:s]: 00:153:18:54:04
Block: 1309324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107755 RingCT/type: yes/0
Extra: 01035a0368d017200e41def9f63d91d22b499a4c7e01bfebf275bd0701d12dd544021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e9f143046ff8977288a129e7ef3254785e1494ba251fe2b2ff49d32192a232e 0.600000000000 1796939 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": 1309334, "vin": [ { "gen": { "height": 1309324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e9f143046ff8977288a129e7ef3254785e1494ba251fe2b2ff49d32192a232e" } } ], "extra": [ 1, 3, 90, 3, 104, 208, 23, 32, 14, 65, 222, 249, 246, 61, 145, 210, 43, 73, 154, 76, 126, 1, 191, 235, 242, 117, 189, 7, 1, 209, 45, 213, 68, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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