Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b8242c9447113714d1f95d6ad04ac50a019c01d32ba5c50af4af94f8d30879

Tx prefix hash: 44bf30a569b9c74b40fe35496814a0286690a3b83c7a84eed14e1adedd3b9763
Tx public key: e227c88f617f37af9e0db64afb8b8e70a31b51eb1de649048c7530768c16d3b6
Timestamp: 1580376600 Timestamp [UCT]: 2020-01-30 09:30:00 Age [y:d:h:m:s]: 04:337:15:12:51
Block: 55249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132264 RingCT/type: yes/0
Extra: 01e227c88f617f37af9e0db64afb8b8e70a31b51eb1de649048c7530768c16d3b6021100000002391a8d0e000000000000000000

1 output(s) for total of 402.690863174000 dcy

stealth address amount amount idx
00: 10eddb800510f18cc49823225828fe76e833f79af32fb6fd83af0f6bc967a1d5 402.690863174000 102035 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": 55259, "vin": [ { "gen": { "height": 55249 } } ], "vout": [ { "amount": 402690863174, "target": { "key": "10eddb800510f18cc49823225828fe76e833f79af32fb6fd83af0f6bc967a1d5" } } ], "extra": [ 1, 226, 39, 200, 143, 97, 127, 55, 175, 158, 13, 182, 74, 251, 139, 142, 112, 163, 27, 81, 235, 29, 230, 73, 4, 140, 117, 48, 118, 140, 22, 211, 182, 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