Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be97b0e3cefacc9ccf39735264984fabd53e039dc2b4cfc55040b9df5852a75e

Tx prefix hash: f3c53110005db9c22006d57ed57cd26785d2a51e6282ea910692aa51d628acf0
Tx public key: e968c57c2f9f099454d3f15ca49d3433265250d43f54885aeb025a7f01df2eae
Timestamp: 1728754115 Timestamp [UCT]: 2024-10-12 17:28:35 Age [y:d:h:m:s]: 00:166:20:34:46
Block: 1130134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119029 RingCT/type: yes/0
Extra: 01e968c57c2f9f099454d3f15ca49d3433265250d43f54885aeb025a7f01df2eae02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f31fe472dc5239d6f880753bb61af0e7699ed0420eb72cf61a06d03dae4780a4 0.600000000000 1613007 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": 1130144, "vin": [ { "gen": { "height": 1130134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f31fe472dc5239d6f880753bb61af0e7699ed0420eb72cf61a06d03dae4780a4" } } ], "extra": [ 1, 233, 104, 197, 124, 47, 159, 9, 148, 84, 211, 241, 92, 164, 157, 52, 51, 38, 82, 80, 212, 63, 84, 136, 90, 235, 2, 90, 127, 1, 223, 46, 174, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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