Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33e9533b242c66bd74310853e1a779db84608a4fa9ca1fc114aaf71e136e628

Tx prefix hash: e291183fb88de192543a2926df3d23652a83dcea75fed2f24f12ed358e7dbf9d
Tx public key: 7f9b666d0a4cae755436a53e84f0aead232baead0058d4aa4d314aa98ebb9ebc
Timestamp: 1729542321 Timestamp [UCT]: 2024-10-21 20:25:21 Age [y:d:h:m:s]: 00:033:17:41:25
Block: 1136624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24114 RingCT/type: yes/0
Extra: 017f9b666d0a4cae755436a53e84f0aead232baead0058d4aa4d314aa98ebb9ebc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d3c6cba0cd018a0707813734f4ae290e2aefbd8ca1e7625b07e81e18e493146 0.600000000000 1619971 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": 1136634, "vin": [ { "gen": { "height": 1136624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d3c6cba0cd018a0707813734f4ae290e2aefbd8ca1e7625b07e81e18e493146" } } ], "extra": [ 1, 127, 155, 102, 109, 10, 76, 174, 117, 84, 54, 165, 62, 132, 240, 174, 173, 35, 43, 174, 173, 0, 88, 212, 170, 77, 49, 74, 169, 142, 187, 158, 188, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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