Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58cfd8a8e4b8729a429182650f9266298ce9d683f2b0bcbc686265c45ccaad9

Tx prefix hash: 931d80aa57640c2a026daeff8120e4f79dfd5f777ab0603861c13e269d23a091
Tx public key: 1a2fd045854919103c9abe9f1d04d215dfe039be46b4c187da9eaff0aa8394b9
Timestamp: 1712539625 Timestamp [UCT]: 2024-04-08 01:27:05 Age [y:d:h:m:s]: 00:264:22:16:03
Block: 995678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189665 RingCT/type: yes/0
Extra: 011a2fd045854919103c9abe9f1d04d215dfe039be46b4c187da9eaff0aa8394b902110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe0426019f3c129aeb7be68f03ad67c1cff3d55789d6843cc4cd6e312523d2e3 0.600000000000 1456092 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": 995688, "vin": [ { "gen": { "height": 995678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0426019f3c129aeb7be68f03ad67c1cff3d55789d6843cc4cd6e312523d2e3" } } ], "extra": [ 1, 26, 47, 208, 69, 133, 73, 25, 16, 60, 154, 190, 159, 29, 4, 210, 21, 223, 224, 57, 190, 70, 180, 193, 135, 218, 158, 175, 240, 170, 131, 148, 185, 2, 17, 0, 0, 0, 11, 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