Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb2b7b169de41bf2b9fecdabd284497daf3bdb59af8750c98c5bd7cd6fa9ba60

Tx prefix hash: 4c16b265ec7b8dd7932551712f8e8794a3556c376746467a15f3e5b83976cac0
Tx public key: 3f9f9a31162ba7b6ff8c9f527dfdca465ff7d1cee6145b63457c46fa98cfdbd6
Timestamp: 1706649775 Timestamp [UCT]: 2024-01-30 21:22:55 Age [y:d:h:m:s]: 01:345:16:10:18
Block: 946856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505935 RingCT/type: yes/0
Extra: 013f9f9a31162ba7b6ff8c9f527dfdca465ff7d1cee6145b63457c46fa98cfdbd602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af5a12677fe6e1edcdd2ecbc347a2aff1944769aafaeec15dd73dd5a14bf7424 0.600000000000 1405196 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": 946866, "vin": [ { "gen": { "height": 946856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af5a12677fe6e1edcdd2ecbc347a2aff1944769aafaeec15dd73dd5a14bf7424" } } ], "extra": [ 1, 63, 159, 154, 49, 22, 43, 167, 182, 255, 140, 159, 82, 125, 253, 202, 70, 95, 247, 209, 206, 230, 20, 91, 99, 69, 124, 70, 250, 152, 207, 219, 214, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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