Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0028a6743a97ae4d13ff0f022cd4a5775cd7a0d313c70addf9856a3c1fd3a11d

Tx prefix hash: 820e4bfefcbfcf6d80c4e61e15f212826d4682da0eca2dbf3c3d1c281686f604
Tx public key: 737f981190655addf7c19e67b74bd8b8543299e26866df5c5709acb5bf76ec23
Timestamp: 1736170068 Timestamp [UCT]: 2025-01-06 13:27:48 Age [y:d:h:m:s]: 00:297:12:01:20
Block: 1191492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210118 RingCT/type: yes/0
Extra: 01737f981190655addf7c19e67b74bd8b8543299e26866df5c5709acb5bf76ec23021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2799dbc2a4f2bda267a8b620ba8b89e72d9316442a677893acd527b9c9f8fabe 0.600000000000 1678031 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": 1191502, "vin": [ { "gen": { "height": 1191492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2799dbc2a4f2bda267a8b620ba8b89e72d9316442a677893acd527b9c9f8fabe" } } ], "extra": [ 1, 115, 127, 152, 17, 144, 101, 90, 221, 247, 193, 158, 103, 183, 75, 216, 184, 84, 50, 153, 226, 104, 102, 223, 92, 87, 9, 172, 181, 191, 118, 236, 35, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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