Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb00f61caafb4c228488a16655d0481b36c9aab882f71d8d6e02b45d0b06480d

Tx prefix hash: 988aa919361f34d895b7e2a9786f1b80c656224edd41c0181a8ac7e2438ced84
Tx public key: e722f1ecbbac492bd2ae9f52f00b00fda512aa97d13de51dff260b0e4555fc51
Timestamp: 1704225694 Timestamp [UCT]: 2024-01-02 20:01:34 Age [y:d:h:m:s]: 01:090:19:08:59
Block: 926769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326007 RingCT/type: yes/0
Extra: 01e722f1ecbbac492bd2ae9f52f00b00fda512aa97d13de51dff260b0e4555fc510211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46a0939b50bbe4b7672d8353b4796b2a689b077f544256d921ecd9b3a0ad5eab 0.600000000000 1384567 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": 926779, "vin": [ { "gen": { "height": 926769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46a0939b50bbe4b7672d8353b4796b2a689b077f544256d921ecd9b3a0ad5eab" } } ], "extra": [ 1, 231, 34, 241, 236, 187, 172, 73, 43, 210, 174, 159, 82, 240, 11, 0, 253, 165, 18, 170, 151, 209, 61, 229, 29, 255, 38, 11, 14, 69, 85, 252, 81, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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