Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c6b44f743db2a6584cd055dd4d3444c42045f7d0dbf69bc9ecf024b9091da48

Tx prefix hash: 8def3559cc83ec83c2163855773dd3726b2b9adc9f69d26d7827139f1c4d75b0
Tx public key: 5b3f35d1da90ce5354da45b50e26e96614d9f5b2eb227887e69388e8058904b7
Timestamp: 1682372391 Timestamp [UCT]: 2023-04-24 21:39:51 Age [y:d:h:m:s]: 01:359:08:18:17
Block: 745849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518098 RingCT/type: yes/0
Extra: 015b3f35d1da90ce5354da45b50e26e96614d9f5b2eb227887e69388e8058904b7021100000003faf35c9c000000000000000000

1 output(s) for total of 2.073446603000 dcy

stealth address amount amount idx
00: 8ec8fc5d12261d913d410615b211c18f42e0f7a3055c32624948c0adc864fa58 2.073446603000 1193340 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": 745859, "vin": [ { "gen": { "height": 745849 } } ], "vout": [ { "amount": 2073446603, "target": { "key": "8ec8fc5d12261d913d410615b211c18f42e0f7a3055c32624948c0adc864fa58" } } ], "extra": [ 1, 91, 63, 53, 209, 218, 144, 206, 83, 84, 218, 69, 181, 14, 38, 233, 102, 20, 217, 245, 178, 235, 34, 120, 135, 230, 147, 136, 232, 5, 137, 4, 183, 2, 17, 0, 0, 0, 3, 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