Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78d32008bdf638c7ea1c63500f0c71a77a93df064d3587e002a3e1a1ae95c46

Tx prefix hash: 639f1abcbe52926c5cd5d40c6cd065eed2d495fe0f54576fa9729f95956576d9
Tx public key: 3186b4553cdb38ac09217904af7bb2ef3abeffbd75a53d54367877be8b9b69c0
Timestamp: 1696103682 Timestamp [UCT]: 2023-09-30 19:54:42 Age [y:d:h:m:s]: 01:187:10:22:45
Block: 859648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395003 RingCT/type: yes/0
Extra: 013186b4553cdb38ac09217904af7bb2ef3abeffbd75a53d54367877be8b9b69c00211000000054b8f5122000000000000000000

1 output(s) for total of 0.870260604000 dcy

stealth address amount amount idx
00: 734877d16ad3dc7f8cbd33d60c4b78ed1a085dff39aa5f5a500fdaf103f20654 0.870260604000 1313884 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": 859658, "vin": [ { "gen": { "height": 859648 } } ], "vout": [ { "amount": 870260604, "target": { "key": "734877d16ad3dc7f8cbd33d60c4b78ed1a085dff39aa5f5a500fdaf103f20654" } } ], "extra": [ 1, 49, 134, 180, 85, 60, 219, 56, 172, 9, 33, 121, 4, 175, 123, 178, 239, 58, 190, 255, 189, 117, 165, 61, 84, 54, 120, 119, 190, 139, 155, 105, 192, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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