Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4767c9e16fe1416381d2593a55e68b0117156e743703e85c345aca302d9b88

Tx prefix hash: cf17eeb30063b38e7b459375e7dc9c407c0d6ef1856e49dbfab4943741b58290
Tx public key: d0e860181b978c9c04d1be2910dcbd381537477eb577ec4c0a1296242afb39bd
Timestamp: 1580895184 Timestamp [UCT]: 2020-02-05 09:33:04 Age [y:d:h:m:s]: 04:327:02:35:48
Block: 59203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125073 RingCT/type: yes/0
Extra: 01d0e860181b978c9c04d1be2910dcbd381537477eb577ec4c0a1296242afb39bd02110000019ebd0f9f9f000000000000000000

1 output(s) for total of 390.700706241000 dcy

stealth address amount amount idx
00: 884f2c612e961f41d27a0996a38e5e434ec1a8c073c91fa61013ad23e84f8705 390.700706241000 109285 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": 59213, "vin": [ { "gen": { "height": 59203 } } ], "vout": [ { "amount": 390700706241, "target": { "key": "884f2c612e961f41d27a0996a38e5e434ec1a8c073c91fa61013ad23e84f8705" } } ], "extra": [ 1, 208, 232, 96, 24, 27, 151, 140, 156, 4, 209, 190, 41, 16, 220, 189, 56, 21, 55, 71, 126, 181, 119, 236, 76, 10, 18, 150, 36, 42, 251, 57, 189, 2, 17, 0, 0, 1, 158, 189, 15, 159, 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