Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95943f64c82c0812654064ce4473f55657e9e105b6ac9758def7ed5ec295735

Tx prefix hash: cebe27c2079124f0775b6d3276fb3a8740989f85a00e2446b3a0bdbc11dd5cd4
Tx public key: 89a120e876537695f7c9e1622fd88147962d658a4471f03b85ee7a6cee6e595d
Timestamp: 1720802968 Timestamp [UCT]: 2024-07-12 16:49:28 Age [y:d:h:m:s]: 00:225:10:58:54
Block: 1064223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161016 RingCT/type: yes/0
Extra: 0189a120e876537695f7c9e1622fd88147962d658a4471f03b85ee7a6cee6e595d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9f6bdee724e8b4c6d6bb2c4da373c6a6e11a73f82d4da51435dd670169b61ac 0.600000000000 1534746 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": 1064233, "vin": [ { "gen": { "height": 1064223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9f6bdee724e8b4c6d6bb2c4da373c6a6e11a73f82d4da51435dd670169b61ac" } } ], "extra": [ 1, 137, 161, 32, 232, 118, 83, 118, 149, 247, 201, 225, 98, 47, 216, 129, 71, 150, 45, 101, 138, 68, 113, 240, 59, 133, 238, 122, 108, 238, 110, 89, 93, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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