Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a321e6adf45b6f260ea1037dbd5fddca23011f41e469c78e51b56fed9dd69ffd

Tx prefix hash: 977b1421465016a7f5a458f77867d8bae22b7883e14c6a5966f97377732d7e85
Tx public key: 6677d7d3d8560497dff98e3cbb8bbde5ae27597121362b6e6d9e0eda51489dc8
Timestamp: 1751593734 Timestamp [UCT]: 2025-07-04 01:48:54 Age [y:d:h:m:s]: 00:183:10:01:46
Block: 1318303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129430 RingCT/type: yes/0
Extra: 016677d7d3d8560497dff98e3cbb8bbde5ae27597121362b6e6d9e0eda51489dc802110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93ae83418eb67d89a6a07d01ca0085ef3e024a8203018dafad5f7654fb6df0ce 0.600000000000 1805982 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": 1318313, "vin": [ { "gen": { "height": 1318303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93ae83418eb67d89a6a07d01ca0085ef3e024a8203018dafad5f7654fb6df0ce" } } ], "extra": [ 1, 102, 119, 215, 211, 216, 86, 4, 151, 223, 249, 142, 60, 187, 139, 189, 229, 174, 39, 89, 113, 33, 54, 43, 110, 109, 158, 14, 218, 81, 72, 157, 200, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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