Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb5427a1b44273ad6795c96f46f6ef41541e6832e4d737944ccc9cc9d8ec68f8

Tx prefix hash: 9afcbff8da66e3b0f85cbf04ef408d3841ee6bb8e38042e2c3bc85a671b0e50c
Tx public key: 2a885de9d79ce67c36938d44920c75d988aacc610db9fb6bed785a633b8b3870
Timestamp: 1582083538 Timestamp [UCT]: 2020-02-19 03:38:58 Age [y:d:h:m:s]: 04:313:04:44:53
Block: 67809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116357 RingCT/type: yes/0
Extra: 012a885de9d79ce67c36938d44920c75d988aacc610db9fb6bed785a633b8b387002110000001c4943cd9f000000000000000000

1 output(s) for total of 365.865485056000 dcy

stealth address amount amount idx
00: 62c1d999c1c9ad5883eed0d1fd5ddeeeb71ea4281ce5af667721587cc28458f8 365.865485056000 124945 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": 67819, "vin": [ { "gen": { "height": 67809 } } ], "vout": [ { "amount": 365865485056, "target": { "key": "62c1d999c1c9ad5883eed0d1fd5ddeeeb71ea4281ce5af667721587cc28458f8" } } ], "extra": [ 1, 42, 136, 93, 233, 215, 156, 230, 124, 54, 147, 141, 68, 146, 12, 117, 217, 136, 170, 204, 97, 13, 185, 251, 107, 237, 120, 90, 99, 59, 139, 56, 112, 2, 17, 0, 0, 0, 28, 73, 67, 205, 159, 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