Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e7f74687b83120541da57c7cd873db3f2c506ef6fcf84d115ad4b42b79ac41b

Tx prefix hash: 4adbc07c017af9a603a2410020e97cf651eaf9f0c09465dcca3374bc41c74ea6
Tx public key: 1525cd9fdf8b1e1fdc316f5d680b690c930af8bf112b7c33e99bb71b2b41d355
Timestamp: 1717059944 Timestamp [UCT]: 2024-05-30 09:05:44 Age [y:d:h:m:s]: 00:154:04:19:51
Block: 1033180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110371 RingCT/type: yes/0
Extra: 011525cd9fdf8b1e1fdc316f5d680b690c930af8bf112b7c33e99bb71b2b41d35502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9d6616e5cdfa595a72967539c36856d65592d714684d4f24b00df53546ebfbc 0.600000000000 1501643 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": 1033190, "vin": [ { "gen": { "height": 1033180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9d6616e5cdfa595a72967539c36856d65592d714684d4f24b00df53546ebfbc" } } ], "extra": [ 1, 21, 37, 205, 159, 223, 139, 30, 31, 220, 49, 111, 93, 104, 11, 105, 12, 147, 10, 248, 191, 17, 43, 124, 51, 233, 155, 183, 27, 43, 65, 211, 85, 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