Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 332d8b130f6422a310f80da4aa25679309e419be54f2a9241b9ec4acff811a78

Tx prefix hash: a55101559cd2c0603af252d10d6233d684d9aa237f8c8c1f5539c597bf42e8a0
Tx public key: 0b2a797445d50e8394a2096378bd033cfc12f427f05a8fa25325844bebf91bdd
Timestamp: 1700304281 Timestamp [UCT]: 2023-11-18 10:44:41 Age [y:d:h:m:s]: 01:075:00:03:04
Block: 894266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314755 RingCT/type: yes/0
Extra: 010b2a797445d50e8394a2096378bd033cfc12f427f05a8fa25325844bebf91bdd02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.668229288000 dcy

stealth address amount amount idx
00: 2d412a528fcf71ce1fec1e49a728044eb97200f038d28c8a7a2f62849ab704b3 0.668229288000 1350461 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": 894276, "vin": [ { "gen": { "height": 894266 } } ], "vout": [ { "amount": 668229288, "target": { "key": "2d412a528fcf71ce1fec1e49a728044eb97200f038d28c8a7a2f62849ab704b3" } } ], "extra": [ 1, 11, 42, 121, 116, 69, 213, 14, 131, 148, 162, 9, 99, 120, 189, 3, 60, 252, 18, 244, 39, 240, 90, 143, 162, 83, 37, 132, 75, 235, 249, 27, 221, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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