Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589d13a9b679bf508a553ab7c19737451c775400d64ca66a79ab7e0e5dea8889

Tx prefix hash: 36a1b5c1ce03150152c5e897e8439fb66f3779fcf7144dea611cb5298c2a4a69
Tx public key: 62a425cfbe50a6ce3bb1224b4e739bf23d73caa5ffa462f0c28573efa79ef3ce
Timestamp: 1580474030 Timestamp [UCT]: 2020-01-31 12:33:50 Age [y:d:h:m:s]: 04:342:11:09:28
Block: 55674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136102 RingCT/type: yes/0
Extra: 0162a425cfbe50a6ce3bb1224b4e739bf23d73caa5ffa462f0c28573efa79ef3ce021100000002391a8d0e000000000000000000

1 output(s) for total of 401.355992166000 dcy

stealth address amount amount idx
00: 590854d26b0e5798e232f1ee14c364e05062c8774b2a4c79a5c7c7ce28f4990d 401.355992166000 102738 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": 55684, "vin": [ { "gen": { "height": 55674 } } ], "vout": [ { "amount": 401355992166, "target": { "key": "590854d26b0e5798e232f1ee14c364e05062c8774b2a4c79a5c7c7ce28f4990d" } } ], "extra": [ 1, 98, 164, 37, 207, 190, 80, 166, 206, 59, 177, 34, 75, 78, 115, 155, 242, 61, 115, 202, 165, 255, 164, 98, 240, 194, 133, 115, 239, 167, 158, 243, 206, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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