Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7596b138c792a4c7d384421c1ee78c42940d65ca6c2bb960501f657b5726189

Tx prefix hash: b5588725a640a3489427d74c256d2889e2d3de176d5da1407e015c52fd0b19cd
Tx public key: 7832adba50c6be649a3f0a3d5a987d59cc8ea2ae20181f8e3b47033ac091e96c
Timestamp: 1729595944 Timestamp [UCT]: 2024-10-22 11:19:04 Age [y:d:h:m:s]: 00:154:16:49:09
Block: 1137078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110347 RingCT/type: yes/0
Extra: 017832adba50c6be649a3f0a3d5a987d59cc8ea2ae20181f8e3b47033ac091e96c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 856389a5e4bf66ad58c5e21d0a279508670b5c43b6eb9364955d8793bb83686b 0.600000000000 1620503 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": 1137088, "vin": [ { "gen": { "height": 1137078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "856389a5e4bf66ad58c5e21d0a279508670b5c43b6eb9364955d8793bb83686b" } } ], "extra": [ 1, 120, 50, 173, 186, 80, 198, 190, 100, 154, 63, 10, 61, 90, 152, 125, 89, 204, 142, 162, 174, 32, 24, 31, 142, 59, 71, 3, 58, 192, 145, 233, 108, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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