Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c46cf6fe5c994287a022600f7d57b47866b0f72c80ffd46fd6342260379ba2

Tx prefix hash: 88cdb1a5e6e20b61e5f28a09e966aa0e73fc8ee94dcaf5d4cfaf02b8f970782e
Tx public key: a3fb9c504afc460a3a5333cd1bbd09676eb3678fcb2a9f3d7826f74c368abaf5
Timestamp: 1708457494 Timestamp [UCT]: 2024-02-20 19:31:34 Age [y:d:h:m:s]: 00:281:23:52:28
Block: 961865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201893 RingCT/type: yes/0
Extra: 01a3fb9c504afc460a3a5333cd1bbd09676eb3678fcb2a9f3d7826f74c368abaf50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 449c9269f0613c0e54f66659df1c17cd539dd82c947d579c4c865436ca322929 0.600000000000 1421478 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": 961875, "vin": [ { "gen": { "height": 961865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "449c9269f0613c0e54f66659df1c17cd539dd82c947d579c4c865436ca322929" } } ], "extra": [ 1, 163, 251, 156, 80, 74, 252, 70, 10, 58, 83, 51, 205, 27, 189, 9, 103, 110, 179, 103, 143, 203, 42, 159, 61, 120, 38, 247, 76, 54, 138, 186, 245, 2, 17, 0, 0, 0, 1, 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