Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64232c94f63a1fc481328d42e408af50ac5f060a540fb1f3e4d6b13f19991e3a

Tx prefix hash: 1926c6fd43b8f493c29026fbc2c2aabddcd05d5ee6762f95f5f7f4dcc797febe
Tx public key: 767cd95dccd676623bdaa742a751bf22737320b861d8b77b1e80a51b89cccdd7
Timestamp: 1752148588 Timestamp [UCT]: 2025-07-10 11:56:28 Age [y:d:h:m:s]: 00:181:00:16:30
Block: 1322604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128003 RingCT/type: yes/0
Extra: 01767cd95dccd676623bdaa742a751bf22737320b861d8b77b1e80a51b89cccdd7021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 024eea1cab885fe116b1fb80c19f5a04132af0f2af709a7cc1d58330d3f524c5 0.600000000000 1810335 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": 1322614, "vin": [ { "gen": { "height": 1322604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "024eea1cab885fe116b1fb80c19f5a04132af0f2af709a7cc1d58330d3f524c5" } } ], "extra": [ 1, 118, 124, 217, 93, 204, 214, 118, 98, 59, 218, 167, 66, 167, 81, 191, 34, 115, 115, 32, 184, 97, 216, 183, 123, 30, 128, 165, 27, 137, 204, 205, 215, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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