Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b3a1e3be1c16c0e26f1fce0318e34cb8898079957a36e0d9511ff599f89cf77

Tx prefix hash: 4123d591fcd278c04967711540e9ec01fea0da39963e112634cd97bd598f470e
Tx public key: d4fba6d69e9cab4b06b05f89df872c3f34244fabdc3e0f25f59ac4ce000a779b
Timestamp: 1577793905 Timestamp [UCT]: 2019-12-31 12:05:05 Age [y:d:h:m:s]: 05:076:10:06:09
Block: 35708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204429 RingCT/type: yes/0
Extra: 01d4fba6d69e9cab4b06b05f89df872c3f34244fabdc3e0f25f59ac4ce000a779b0211000000304fb58672000000000000000000

1 output(s) for total of 467.454338661000 dcy

stealth address amount amount idx
00: b2faefeef01b919d7a3b46d6a82fbd1196bf123b3e3bdcf8fee7db73b38892a3 467.454338661000 60283 of 0

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": 35718, "vin": [ { "gen": { "height": 35708 } } ], "vout": [ { "amount": 467454338661, "target": { "key": "b2faefeef01b919d7a3b46d6a82fbd1196bf123b3e3bdcf8fee7db73b38892a3" } } ], "extra": [ 1, 212, 251, 166, 214, 158, 156, 171, 75, 6, 176, 95, 137, 223, 135, 44, 63, 52, 36, 79, 171, 220, 62, 15, 37, 245, 154, 196, 206, 0, 10, 119, 155, 2, 17, 0, 0, 0, 48, 79, 181, 134, 114, 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