Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f88641bc5e05c7c43be1031725d9113a496b8f0f3119883cc615ceffd1fa7ba

Tx prefix hash: f2976b571bad7a8e7d0e7a832138b664e5f6aabd2dac80348458874b13832671
Tx public key: f1f9d61e5a35be7d2c1be8b0405635502f03ec0a53847484e357504226a19234
Timestamp: 1706899541 Timestamp [UCT]: 2024-02-02 18:45:41 Age [y:d:h:m:s]: 01:110:17:27:07
Block: 948930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340246 RingCT/type: yes/0
Extra: 01f1f9d61e5a35be7d2c1be8b0405635502f03ec0a53847484e357504226a1923402110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 190e631f0f0ca76a416e28b3bfd2560aceb13aeacb9b803333d17c874e4ba5f9 0.600000000000 1407446 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": 948940, "vin": [ { "gen": { "height": 948930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "190e631f0f0ca76a416e28b3bfd2560aceb13aeacb9b803333d17c874e4ba5f9" } } ], "extra": [ 1, 241, 249, 214, 30, 90, 53, 190, 125, 44, 27, 232, 176, 64, 86, 53, 80, 47, 3, 236, 10, 83, 132, 116, 132, 227, 87, 80, 66, 38, 161, 146, 52, 2, 17, 0, 0, 0, 10, 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