Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12649873a5a9918053f22bcab267b1384d870b827b91ed98c7a9b9c2f4c1f79e

Tx prefix hash: 072ae4508756156093ad00fd90d26d0829934bc1bb7976f72c903f82a65cbc3b
Tx public key: 10d244e832d7f1776b7fb9c44b8609b5efef419063bf7010c5ac8b94c56ad4ce
Timestamp: 1726252736 Timestamp [UCT]: 2024-09-13 18:38:56 Age [y:d:h:m:s]: 00:202:22:36:57
Block: 1109390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144875 RingCT/type: yes/0
Extra: 0110d244e832d7f1776b7fb9c44b8609b5efef419063bf7010c5ac8b94c56ad4ce021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3d0ca1036e0a1f8a29dcdda778f13b96e9f072e306f1f742618b092d8c7675e 0.600000000000 1587629 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": 1109400, "vin": [ { "gen": { "height": 1109390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d0ca1036e0a1f8a29dcdda778f13b96e9f072e306f1f742618b092d8c7675e" } } ], "extra": [ 1, 16, 210, 68, 232, 50, 215, 241, 119, 107, 127, 185, 196, 75, 134, 9, 181, 239, 239, 65, 144, 99, 191, 112, 16, 197, 172, 139, 148, 197, 106, 212, 206, 2, 17, 0, 0, 0, 7, 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