Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6768ca9c24b8b0887b6dd6586bfd39c811f538f8238951638cff35a30ab8fce1

Tx prefix hash: 0dc51baa5ad0689ecbac10dfa94bf66e41680b999b13fc02516cf4623e00bfe0
Tx public key: ae5a04ef1c72bfe42aaf58ea8a64fbfc073c7de9f579cf580d0710adbf239f7d
Timestamp: 1711330495 Timestamp [UCT]: 2024-03-25 01:34:55 Age [y:d:h:m:s]: 01:018:12:17:34
Block: 985704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274180 RingCT/type: yes/0
Extra: 01ae5a04ef1c72bfe42aaf58ea8a64fbfc073c7de9f579cf580d0710adbf239f7d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b5a60484257f0f7f9f4f311116569aaa958375df78c18428c8322d61e6a5da7 0.600000000000 1445921 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": 985714, "vin": [ { "gen": { "height": 985704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b5a60484257f0f7f9f4f311116569aaa958375df78c18428c8322d61e6a5da7" } } ], "extra": [ 1, 174, 90, 4, 239, 28, 114, 191, 228, 42, 175, 88, 234, 138, 100, 251, 252, 7, 60, 125, 233, 245, 121, 207, 88, 13, 7, 16, 173, 191, 35, 159, 125, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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