Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a93ebfe58faf831dc160eedc5e6f4be2733c6182692a4d67858f873c8d51495a

Tx prefix hash: 62d97a98e6b0b5b8ea2b633d4b591eb9ffa403aad398a5ccfb0d331c14e9b247
Tx public key: 05bd433371ca081bab7dae8333a45d9a78f1536a70378cdaa0c633dd09900948
Timestamp: 1725925543 Timestamp [UCT]: 2024-09-09 23:45:43 Age [y:d:h:m:s]: 00:218:00:46:04
Block: 1106690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155653 RingCT/type: yes/0
Extra: 0105bd433371ca081bab7dae8333a45d9a78f1536a70378cdaa0c633dd09900948021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0a8403e2a3e7343827a531a16cd2f7f80eafe8f6912bcd8f4a7b17c2553e36a 0.600000000000 1584291 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": 1106700, "vin": [ { "gen": { "height": 1106690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0a8403e2a3e7343827a531a16cd2f7f80eafe8f6912bcd8f4a7b17c2553e36a" } } ], "extra": [ 1, 5, 189, 67, 51, 113, 202, 8, 27, 171, 125, 174, 131, 51, 164, 93, 154, 120, 241, 83, 106, 112, 55, 140, 218, 160, 198, 51, 221, 9, 144, 9, 72, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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