Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa08bdeec26d7aab46ef88066459e95d000b3deaa1c93b0a5b9768a13617d23

Tx prefix hash: a34ea3f0bb4b7e37a064756d06000ac010bd68ea14d9bf1a3e1075d0c964bd25
Tx public key: 979b52909efb2f8e87cec1f2bce88308c81ca23957f5df1d7a46e93178b71fe0
Timestamp: 1759853807 Timestamp [UCT]: 2025-10-07 16:16:47 Age [y:d:h:m:s]: 00:040:11:09:42
Block: 1384839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28979 RingCT/type: yes/0
Extra: 01979b52909efb2f8e87cec1f2bce88308c81ca23957f5df1d7a46e93178b71fe0021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d2f452079593b3318d46dd328837b95041eeecc357acacbb204f45bfad1013 0.600000000000 1872996 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": 1384849, "vin": [ { "gen": { "height": 1384839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d2f452079593b3318d46dd328837b95041eeecc357acacbb204f45bfad1013" } } ], "extra": [ 1, 151, 155, 82, 144, 158, 251, 47, 142, 135, 206, 193, 242, 188, 232, 131, 8, 200, 28, 162, 57, 87, 245, 223, 29, 122, 70, 233, 49, 120, 183, 31, 224, 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