Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3ee3fa2e9af0bca589a1a61588d31e4caff2ffca3de49f8c49a7123952bda9b

Tx prefix hash: 51643562047b55eece3fd1c8fa92277e04f027ff949519262dc20a66570be1e6
Tx public key: d3b84552cfa6b3b27c756eb0fbac2f2d306237c16ea5d36588e51c27e21b51d3
Timestamp: 1703799472 Timestamp [UCT]: 2023-12-28 21:37:52 Age [y:d:h:m:s]: 01:059:08:59:06
Block: 923244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303507 RingCT/type: yes/0
Extra: 01d3b84552cfa6b3b27c756eb0fbac2f2d306237c16ea5d36588e51c27e21b51d30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30234a26a08a03381ad15c0bb94a67f9f2fe331bed4ae85582b47e164cc005eb 0.600000000000 1380972 of 15

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": 923254, "vin": [ { "gen": { "height": 923244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30234a26a08a03381ad15c0bb94a67f9f2fe331bed4ae85582b47e164cc005eb" } } ], "extra": [ 1, 211, 184, 69, 82, 207, 166, 179, 178, 124, 117, 110, 176, 251, 172, 47, 45, 48, 98, 55, 193, 110, 165, 211, 101, 136, 229, 28, 39, 226, 27, 81, 211, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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