Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76abe608c449fd79ef8c3d9147499c2104d4848fbd1f7b93b32dfd4bb02ce095

Tx prefix hash: 1d9675ce6c1fb56bb3e2c8e05ee91de85c3abcb3fb405080a100a8af791d38d9
Tx public key: d9cae279daca348834ea7e6da7740a8bcaa5751e9a671b0115841dce375921b5
Timestamp: 1745237161 Timestamp [UCT]: 2025-04-21 12:06:01 Age [y:d:h:m:s]: 00:206:01:36:18
Block: 1266263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145000 RingCT/type: yes/0
Extra: 01d9cae279daca348834ea7e6da7740a8bcaa5751e9a671b0115841dce375921b50211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9296f56e3cdef2590f62d45f9ee1ebfa63d3b3c505719b6069215a30617462ad 0.600000000000 1753484 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": 1266273, "vin": [ { "gen": { "height": 1266263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9296f56e3cdef2590f62d45f9ee1ebfa63d3b3c505719b6069215a30617462ad" } } ], "extra": [ 1, 217, 202, 226, 121, 218, 202, 52, 136, 52, 234, 126, 109, 167, 116, 10, 139, 202, 165, 117, 30, 154, 103, 27, 1, 21, 132, 29, 206, 55, 89, 33, 181, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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