Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87fe46eca85671c2299cbf6396f6073de1e4cba024fc953f4e5ee62bfe58de9

Tx prefix hash: 2a8684db555758d2a5c7795a6967b01f7fd104e9d7c40e7b452239748fb03a51
Tx public key: 6e04f0fd6857b985966225a53f1b358017bc3ffa5f226168f89211ccc0c68254
Timestamp: 1580975607 Timestamp [UCT]: 2020-02-06 07:53:27 Age [y:d:h:m:s]: 04:327:22:03:10
Block: 59582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125942 RingCT/type: yes/0
Extra: 016e04f0fd6857b985966225a53f1b358017bc3ffa5f226168f89211ccc0c68254021100000003026b59f3000000000000000000

1 output(s) for total of 389.565886231000 dcy

stealth address amount amount idx
00: 503be659497808cfb3b51ca6e4b8fe10c1135954e0b84105014bf69c68038b37 389.565886231000 110014 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": 59592, "vin": [ { "gen": { "height": 59582 } } ], "vout": [ { "amount": 389565886231, "target": { "key": "503be659497808cfb3b51ca6e4b8fe10c1135954e0b84105014bf69c68038b37" } } ], "extra": [ 1, 110, 4, 240, 253, 104, 87, 185, 133, 150, 98, 37, 165, 63, 27, 53, 128, 23, 188, 63, 250, 95, 34, 97, 104, 248, 146, 17, 204, 192, 198, 130, 84, 2, 17, 0, 0, 0, 3, 2, 107, 89, 243, 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