Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0436104d567407c4ded539835ea58994b87f34a3eb7a5d1e25d5a5909a858454

Tx prefix hash: d8cb380f158c6dd4ef39bc9a5040f824fd8c5fa463cb7f4148a8adf522963d7e
Tx public key: 969e3cac9dc5bc6c963725d26aadd8157c3a7d9dec46802c5da55cd109b7485d
Timestamp: 1726442544 Timestamp [UCT]: 2024-09-15 23:22:24 Age [y:d:h:m:s]: 00:236:00:52:27
Block: 1110965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168544 RingCT/type: yes/0
Extra: 01969e3cac9dc5bc6c963725d26aadd8157c3a7d9dec46802c5da55cd109b7485d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ec51e46845cfaa8677540d888407d6ea79c90ff1eeb83f7f99c53c41e993ae1 0.600000000000 1589758 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": 1110975, "vin": [ { "gen": { "height": 1110965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ec51e46845cfaa8677540d888407d6ea79c90ff1eeb83f7f99c53c41e993ae1" } } ], "extra": [ 1, 150, 158, 60, 172, 157, 197, 188, 108, 150, 55, 37, 210, 106, 173, 216, 21, 124, 58, 125, 157, 236, 70, 128, 44, 93, 165, 92, 209, 9, 183, 72, 93, 2, 17, 0, 0, 0, 4, 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