Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c558f9b49eea57f88ff39f1a0513e0a79ae72d1632f9e285964a47931b98f77d

Tx prefix hash: c5108a500441dd49451921d9136f7959f89c209cd897a0d3609736a7cd15e088
Tx public key: 6d3d59d3dfc5dd4bb1df5a5c6ad7a623c7a954861c06c4bf4deb29ed49dccfe7
Timestamp: 1727908502 Timestamp [UCT]: 2024-10-02 22:35:02 Age [y:d:h:m:s]: 00:226:07:17:31
Block: 1123123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161565 RingCT/type: yes/0
Extra: 016d3d59d3dfc5dd4bb1df5a5c6ad7a623c7a954861c06c4bf4deb29ed49dccfe7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82b18eafcc29ae7aac7e66c7aac9d94544de4f8538f0c88c9b12d77a44a51f67 0.600000000000 1605656 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": 1123133, "vin": [ { "gen": { "height": 1123123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82b18eafcc29ae7aac7e66c7aac9d94544de4f8538f0c88c9b12d77a44a51f67" } } ], "extra": [ 1, 109, 61, 89, 211, 223, 197, 221, 75, 177, 223, 90, 92, 106, 215, 166, 35, 199, 169, 84, 134, 28, 6, 196, 191, 77, 235, 41, 237, 73, 220, 207, 231, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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