Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09c1d9a7f7e91fa25e680f865d0867f83b2c920a133ceb576761169071a51be

Tx prefix hash: 4076db930c841d4b4d0f981935e7c8f50d941787adb8dae0bca91edd4d3d27f6
Tx public key: 27b47b0aececc0538f485c0b7939b83ef63cfbe071a8f5751a931d43a82ca9b6
Timestamp: 1713401477 Timestamp [UCT]: 2024-04-18 00:51:17 Age [y:d:h:m:s]: 01:058:17:27:03
Block: 1002834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302870 RingCT/type: yes/0
Extra: 0127b47b0aececc0538f485c0b7939b83ef63cfbe071a8f5751a931d43a82ca9b602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e31a8500040851d41d87cdf1466503c629a73b99af9147f9f227509694f9fe3 0.600000000000 1463362 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": 1002844, "vin": [ { "gen": { "height": 1002834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e31a8500040851d41d87cdf1466503c629a73b99af9147f9f227509694f9fe3" } } ], "extra": [ 1, 39, 180, 123, 10, 236, 236, 192, 83, 143, 72, 92, 11, 121, 57, 184, 62, 246, 60, 251, 224, 113, 168, 245, 117, 26, 147, 29, 67, 168, 44, 169, 182, 2, 17, 0, 0, 0, 1, 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