Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae15b902dec05bf069235707eb14c9ff23cf4c87a618b0adbe8c4ed47149ab1

Tx prefix hash: 78bb0d47418749d7a6c837fb5c3de074a6b843ac31d6706c8079e716ab91423a
Tx public key: 91b0644180881cac8cf8d4b5c0e532e5839f90adf196c81431322ab3adbe43dd
Timestamp: 1682491335 Timestamp [UCT]: 2023-04-26 06:42:15 Age [y:d:h:m:s]: 01:357:23:04:38
Block: 746839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517098 RingCT/type: yes/0
Extra: 0191b0644180881cac8cf8d4b5c0e532e5839f90adf196c81431322ab3adbe43dd021100000002faf35c9c000000000000000000

1 output(s) for total of 2.057844589000 dcy

stealth address amount amount idx
00: 1d4cbc8e831aa225d80104d94127abe1d3248123fbab5d479b860c080c54aa43 2.057844589000 1194438 of 0

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": 746849, "vin": [ { "gen": { "height": 746839 } } ], "vout": [ { "amount": 2057844589, "target": { "key": "1d4cbc8e831aa225d80104d94127abe1d3248123fbab5d479b860c080c54aa43" } } ], "extra": [ 1, 145, 176, 100, 65, 128, 136, 28, 172, 140, 248, 212, 181, 192, 229, 50, 229, 131, 159, 144, 173, 241, 150, 200, 20, 49, 50, 42, 179, 173, 190, 67, 221, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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