Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df71ba4a36a7e2e9d791e26362f1dd6aaedf8792188a5e48abac7a337448f153

Tx prefix hash: 7a4e7cac4c617f64ded85316619503803cf631b6a5c9b9856fe7fbeedc12c221
Tx public key: ef6a7d872d5f764d2a087ec5665df81f15f64058fd3da5203b50a190d224c38f
Timestamp: 1687067310 Timestamp [UCT]: 2023-06-18 05:48:30 Age [y:d:h:m:s]: 01:213:00:53:37
Block: 784777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413645 RingCT/type: yes/0
Extra: 01ef6a7d872d5f764d2a087ec5665df81f15f64058fd3da5203b50a190d224c38f02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.540664852000 dcy

stealth address amount amount idx
00: 4bf17d0a79fb5c18cb80858cd083317d329852469df5af6f45f3f25f38b31392 1.540664852000 1234678 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": 784787, "vin": [ { "gen": { "height": 784777 } } ], "vout": [ { "amount": 1540664852, "target": { "key": "4bf17d0a79fb5c18cb80858cd083317d329852469df5af6f45f3f25f38b31392" } } ], "extra": [ 1, 239, 106, 125, 135, 45, 95, 118, 77, 42, 8, 126, 197, 102, 93, 248, 31, 21, 246, 64, 88, 253, 61, 165, 32, 59, 80, 161, 144, 210, 36, 195, 143, 2, 17, 0, 0, 0, 1, 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