Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5d714d407faef226a326e47fa465756ea7cbde299f8e90d5d6aea0f2cd2e27

Tx prefix hash: 98b8e23a4fe5c9f4639f0a510503dcd9732e8c1ec7f81a694786abe7b7fc551b
Tx public key: 43e4a590a9777913883f993a0ddfa5eef4403c3d1e5eecce76daa70c1a41ac5d
Timestamp: 1705887156 Timestamp [UCT]: 2024-01-22 01:32:36 Age [y:d:h:m:s]: 01:133:06:00:02
Block: 940519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356390 RingCT/type: yes/0
Extra: 0143e4a590a9777913883f993a0ddfa5eef4403c3d1e5eecce76daa70c1a41ac5d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7efd6e4c28a486c1d080d19965b2cd71ce2c9ee09aa885b009132b59ae7750c9 0.600000000000 1398657 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": 940529, "vin": [ { "gen": { "height": 940519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7efd6e4c28a486c1d080d19965b2cd71ce2c9ee09aa885b009132b59ae7750c9" } } ], "extra": [ 1, 67, 228, 165, 144, 169, 119, 121, 19, 136, 63, 153, 58, 13, 223, 165, 238, 244, 64, 60, 61, 30, 94, 236, 206, 118, 218, 167, 12, 26, 65, 172, 93, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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