Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f12058250423e601175b83cd8994dad618e95e1ce9f9dfad0a3915e017f5a5

Tx prefix hash: 14f9796beb1f0bf19ed3a1a4613ddf005c183d5863399a9c5b16d595244464e2
Tx public key: 98ecacc1dd2167d79bf69ec83786f935f39c52588c7f0e6d65112b4e1761cdd6
Timestamp: 1684891819 Timestamp [UCT]: 2023-05-24 01:30:19 Age [y:d:h:m:s]: 02:193:13:28:25
Block: 766744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658163 RingCT/type: yes/0
Extra: 0198ecacc1dd2167d79bf69ec83786f935f39c52588c7f0e6d65112b4e1761cdd602110000000275e3f0e9000000000000000000

1 output(s) for total of 1.767905374000 dcy

stealth address amount amount idx
00: 983440b8936ccd25edc3ca3c6b1338f779167bd9c11a365ea7b259d4b506e671 1.767905374000 1215807 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": 766754, "vin": [ { "gen": { "height": 766744 } } ], "vout": [ { "amount": 1767905374, "target": { "key": "983440b8936ccd25edc3ca3c6b1338f779167bd9c11a365ea7b259d4b506e671" } } ], "extra": [ 1, 152, 236, 172, 193, 221, 33, 103, 215, 155, 246, 158, 200, 55, 134, 249, 53, 243, 156, 82, 88, 140, 127, 14, 109, 101, 17, 43, 78, 23, 97, 205, 214, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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